Subject: Updated SNA NAU MIB WG Charter

From: "Bill Kwan" <[email-masked]>
Date: Tue, 2 Apr 1996 14:56:57 +0000

Steve,

Here is an updated charter for the SNA NAU MIB WG. Thanks.

Regards,
Bill

-------------- Enclosure number 1 ----------------

SNA NAU Services MIB (snanau)
-----------------------------
 
 Charter 
 
 Current status: active working group
 
 Chair(s):
     Bill Kwan <[email-masked]>
 
 Network Management Area Director(s): 
     Deirdre Kostick  <[email-masked]>
 
 Area Advisor
     <none>
 
 Mailing lists: 
     General Discussion:[email-masked] (SNA NAU/APPC MIBs)
			[email-masked] 
					(APPN/HPR MIBs)
     To Subscribe:      [email-masked] (SNA NAU/APPC MIBs)
			[email-masked] (APPN/HPR MIBs)
     Archive:           ftp://ftp.cisco.com/snanaumib/mail-archive 
					(SNA NAU/APPC MIBs)
                        ftp://networking.raleigh.ibm.com/pub/standards/aiw
                            /maillogs/appnmibs.95 (APPN/HPR MIBs)
 
Description of Working Group:
 
     The SNA NAU MIB Working Group is chartered to define a
     set of managed objects for SNA Network Accessible Units. These includes
     PUs(Physical Units) such as type 2.0 and 2.1 and LUs(Logical Units)
     such as type 1, 2, 3, and 6.2. These objects will be the minimum
     necessary to provide the ability to monitor and control those
     devices, providing fault, configuration, and performance
     management, and will be consistent with the SNMP framework and
     existing SNMP standards.

     The working group has completed the MIBs for base SNA NAU functions and
     advanced functions for LU Type 6.2 or APPC (Advanced Program-to-Program
     Communication). With the exception of the current work in enhancing the
     SNA NAU MIB, the focus of the working group will be developing
     additional MIBs for managing APPN (Advanced Peer-to-Peer 
     Networking) and HPR (High Performance Routing) nodes. 

     The working group will make sure that its work is aligned with the
     SNA DLC MIB Working Group, due to the close relationship
     between the devices being worked on by the two groups.

 Goals and Milestones: 
 
     APPC MIB
     --------
     Apr 96 Submit the APPC MIB to the IESG for consideration as a Proposed
            Standard.

     SNA NAU MIB
     -----------
     Mar 96 Post -00 Internet-Draft of the SNA NAU MIB with corrections and 
            changes reflecting implementation experiences.
	
     May 96 Post -01 Internet-Draft of SNA NAU MIB and achieve 
            consensus.

     Jun 96 Submit the SNA NAU MIB for NM Directorate review.

     Jul 96 Submit the SNA NAU MIB to the IESG for consideration as a Proposed
	    Standard.
 
     APPN MIB
     --------
     Mar 96 Post -00 Internet-Draft of the APPN MIB.

     Apr 96 Post -01 Internet-Draft of the APPN MIB and achieve 
	    consensus on the APPN MIB.

     May 96 Submit the APPN MIB for NM Directorate review.

     Jun 96 Submit the APPN MIB to the IESG for consideration as a Proposed
	    Standard.

     HPR MIB
     -------
     Jun 96 Post -00 Internet-Draft of the HPR MIB.

     Jul 96 Post -01 Internet-Draft of the HPR MIB and achieve 
            consensus on the HPR MIB.
  
     Aug 96 Submit the HPR MIB for NM Directorate review.

     Aug 96 Submit the HPR MIB to the IESG for consideration as a Proposed 
	    Standard.

Internet-Drafts:

Posted Revised   I-D Title  <Filename>
------ ------- ------------------------------------------
Jul 94 Oct 95  <draft-ietf-snanau-appcmib-04.txt> 
                Definitions of Managed Objects for APPC                        
Mar 96		<draft-ietf-snanau-naumib-00.txt>
		Definitions of Managed Objects for SNA NAUs
Mar 96		<draft-ietf-snanau-appn-00.txt>
		Definitions of Managed Objects for APPN

Request For Comments:

RFC     Stat Published  Title 
------- --   ---------- -----------------------------------------
RFC1666 PS   Aug 94     Definitions of Managed Objects for SNA NAUs using SMIv2
			(obsoletes RFC1665)